In the Administration 
Settings Settings view, select the INVBILLING001 setting and click 
.
In the Edit Configuration form, select the scope level at which you want to add the billing extract mapping file.
You can map additional fields for N4 to extract as part of the billing extract. The field names specified in the mapping file must exactly match the External Tag (case-sensitive) for the N4 field (in the corresponding reporting entity) and have the same data type.
N4 provides:
40 Flex Fields of type String (bexuFlexString01 through bexuFlexString40)
5 Flex Fields of type Date (bexuFlexDate01 through bexuFlexDate05)
5 Flex Fields of type Long (bexuFlexLong01 through bexuFlexLong05)
5 Flex Fields of type Double (bexuFlexDouble01 through bexuFlexDouble05)
The field name specified in the value attribute must exactly match the External Tag (case-sensitive) specified for the field in the corresponding reporting entity. If it is not a valid map, N4 does not extract the field. For example, to map a unit flex field, use the External Tag (case-sensitive) specified for the flex field in the Unit reporting entity.
The following sample billing extract XML mapping displays the format of the available flex fields that you can use to map existing N4 fields. The flexfield-mappings block consists of flex fields of type string, date, and long. For example, the bexuFlexString01 flex field is of the type string and you can only map it to N4 fields that are of the type string.
<?xml version="1.0" encoding="UTF-8"?>
<!--Define the billing flex field mapping here. Billing extract uses this file to store the actual field values to the flex fields in the argo_chargeable_unit_events table. It is the editor's responsibility to type the correct flex field value. Editor should assign the string, date, long column value selection appropriately. If it is not a valid column name in N4, the column will not be extracted.-->
<flexfield-mappings>
<flexfield-mapping id="bexuFlexString01" value="FreightKind"/>
<flexfield-mapping id="bexuFlexString02" value="EquipmentOwner"/>
<flexfield-mapping id="bexuFlexString03" value="UnitFlexString01"/>
<flexfield-mapping id="bexuFlexString04" value=""/>
<flexfield-mapping id="bexuFlexString05" value=""/>
<flexfield-mapping id="bexuFlexDate01" value="InboundCarrierETA"/>
<flexfield-mapping id="bexuFlexDate02" value=""/>
<flexfield-mapping id="bexuFlexDate03" value=""/>
<flexfield-mapping id="bexuFlexDate04" value=""/>
<flexfield-mapping id="bexuFlexDate05" value=""/>
<flexfield-mapping id="bexuFlexLong01" value="EquipmentTareWeightKg"/>
<flexfield-mapping id="bexuFlexLong02" value=""/>
<flexfield-mapping id="bexuFlexLong03" value=""/>
<flexfield-mapping id="bexuFlexLong04" value=""/>
<flexfield-mapping id="bexuFlexLong05" value=""/>
<flexfield-mapping id="bexuFlexDouble01" value=""/>
<flexfield-mapping id="bexuFlexDouble02" value=""/>
<flexfield-mapping id="bexuFlexDouble03" value=""/>
<flexfield-mapping id="bexuFlexDouble04" value=""/>
<flexfield-mapping id="bexuFlexDouble05" value=""/>
</flexfield-mappings>
To load a user-defined billing extract mapping file:
Create the billing extract mapping file using any XML editor.
You can also copy the sample mapping file shown above and edit the fields you want to extract.
In the Administration Settings Settings view, select the INVBILLING001 setting and click .
In the Edit Configuration form, select the scope level at which you want to add the billing extract mapping file.
All the lower scope levels inherit the mapping file.
Click Override to override the existing configuration for the INVBILLING001 setting.
Click Import File to import the billing extract mapping file.
In the Import XML Configuration dialog box, select the billing extract mapping file and click Open.
The text field displays --loaded-- to indicate that the mapping file is associated at the selected scope level.
To remove a loaded file, click Clear.
Click Save.